Skip to content

Conversation

jblomer
Copy link
Contributor

@jblomer jblomer commented Sep 12, 2025

Follow up of #19763

Copy link

github-actions bot commented Sep 12, 2025

Test Results

    21 files      21 suites   3d 18h 32m 26s ⏱️
 3 664 tests  3 661 ✅ 0 💤 3 ❌
75 162 runs  75 154 ✅ 5 💤 3 ❌

For more details on these failures, see this check.

Results for commit 1623541.

♻️ This comment has been updated with latest results.

@jblomer jblomer force-pushed the ntuple-cache-nentries branch from 4d5df2e to 1623541 Compare September 15, 2025 11:44
@@ -82,6 +82,8 @@ private:
/// Retrieving descriptor data from an RNTupleReader is supposed to be for testing and information purposes,
/// not on a hot code path.
std::optional<ROOT::RNTupleDescriptor> fCachedDescriptor;
/// We know that the RNTupleReader is always reading a single RNTuple, so the number of entries is fixed.
ROOT::NTupleSize_t fCachedNEntries = kInvalidNTupleIndex;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this default make sense? Wouldn't 0 be a more apt choice?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, maybe it's fine to just call it fNEntries at this point?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants